Schedule Mapping Page of the Integration Wizard — MS Project
Use this page to define how the fields in the schedule map to the Cobra project.
Project Keys Tab
Use this tab to define the project keys to use when mapping to the schedule. If you are creating a new project, the labels and Cobra validation files on this tab are based on the project information for the selected project. Any control account fields that are not defined in the project are hidden.
When you create a new project, the labels and validation files are based on the template project defined on the Application Preferences dialog box of the application. If no template project is defined, the fields are based on the system defaults for new projects.
| Field | Description |
|---|---|
| Schedule Fields | Use these fields to map the fields in the schedule to their corresponding Cobra fields. Click
 to select a value for each of the fields below:
The values in these fields depend on the date field selected for Baseline and Forecast, and the scheduling tool from which you are importing. You cannot import using the CA3 field unless a template project that defines this field is used or if you are importing into an existing project with this field defined. When you import data from any date field , the following values are available in the Control Account 1-3, Work Package, Milestone, and CAM fields:
|
Cobra File Used for Validation
Use the fields in this column to define the Cobra file to be assigned to the key field in Cobra. If the template does not have the required fields defined, the fields are enabled. Click
to select a file against which to validate each key for new projects.
If you are importing into an existing project or if a template containing these fields has been defined for the application, the fields in this column are populated and disabled.
Resource Name
-
Resource Name: This is the resource name defined in MSP and is the default value being loaded.
-
Code: This loads values from the Code field on the General tab of the Resource Information dialog box in MSP.
-
Resource Text Fields: Any resource-level custom fields with the type “Text” and have values assigned to resources in the MSP project are displayed in the list. This will show both Project and Enterprise level code fields.
-
Resource Outline Codes: Any resource-level outline code custom fields that have values assigned to resources in the MSP Project are shown in the list. The list displays Project- and Enterprise-level code fields.
All resources with the same field value and the same work package mapping will be aggregated into a single resource in Cobra by a class. If you are loading a resource at the Control Account (CA)-level class, the resources will be aggregated at the CA level.
Control Account Codes Tab
Use this tab to map imported data to codes in the Control Account field. This tab displays a grid with lines representing the code assignments associated with the selected project.
When you create a new project, the codes defined on the template project display in the grid. If no code is defined for the selected project, or if you are creating a new project where no template is defined, an error message displays saying that there are no control account codes defined for the project.
| Field | Description |
|---|---|
| Prompt | When you import into an existing project, the prompts for any predefined codes from the project information are displayed in the grid. |
| Schedule Fields | Use the fields in this column to map fields in the schedule that contain the code assignment. You can either click
to select a schedule field, or enter the name of the schedule field. An invalid schedule field results in an error.
Make sure that you have selected Code Assignments and User Fields on the Action Selection page if codes are assigned to the project. |
Work Package Codes Tab
Use this tab to map imported data to codes in the Work Package field. This tab displays a grid with lines representing the code assignments associated with the selected project.
When you create a new project, the codes defined in the template project are displayed in the grid. If no code is defined for the selected project or if you are creating a new project where no template is defined, an error message displays saying that there are no work package codes defined for the project.
| Field | Description |
|---|---|
| Prompt | When you import into an existing project, the prompts for any predefined codes from the project information display in the grid. |
| Schedule Fields | Use the fields in this column to map fields in the schedule that contain the code assignment. You can either click
to select a schedule field or enter the name of the schedule field. An invalid schedule field results in an error.
Make sure that you have selected Control Account and Work Package on the Action Selection page if work packages are assigned to the project. |
User Fields Tab
Use this tab to map schedule fields to the Cobra user fields. The User Fields grid displays the following columns:
| Column | Description |
|---|---|
| Cobra User Field | This column displays the list of the Cobra user fields. |
| Schedule Field | Use this column to select a schedule field to map against the Cobra user field. You can either click
to select a schedule field or enter the name of the schedule field. The
User Character Fields [1-10] lookup dialog box will only display text code fields defined in the schedule. The
User Number Fields [1-10] lookup dialog box will only display numeric code fields defined in the schedule. The
User Date Fields [1-10] lookup dialog box will only display date code fields defined in the schedule.
The User Field grid displays only of you select Code Assignments and User Fields on the Action Selection page. Note: You must first run the required script to display
User Character Fields [6-10],
User Number Fields [6-10], or
User Date Fields [6-10]. Refer to
Additional User Fields for instructions on how to configure Cobra to use these additional fields.
User Character Fields can be mapped to:
User Date Fields can be mapped to:
User Number Fields can be mapped to:
|